System and method for implementing multimedia calling line identification presentation service

ABSTRACT

Implementing a multimedia calling line identification presentation service. A multimedia resource notification module obtains a storage address of a multimedia resource that is stored by a resource storage entity and that is subscribed to by a calling terminal, and sends the storage address of the multimedia resource to a resource playing entity. A service management module establishes a media channel between the resource playing entity and the called terminal for playing the multimedia resource. Establishing the media channel includes sending multimedia session information to the called terminal, the multimedia session information having been received by the service management module from the resource playing entity. Establishing the media channel also includes sending negotiated multimedia session information to the resource playing entity, the negotiated multimedia session information having been received by the service management module from the called terminal.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.11/698,891, filed Jan. 29, 2007, and entitled “SYSTEM AND METHOD FORIMPLEMENTING MULTIMEDIA CALLING LINE IDENTIFICATION PRESENTATIONSERVICE,” which application claims the priority of Chinese PatentApplication No. 200610057699.0, filed Feb. 24, 2006. The entire contentsof each of the foregoing applications are incorporated by referenceherein in their entirety.

FIELD OF THE INVENTION

The present invention relates to the system and method for implementinga Multimedia Calling Line Identification Presentation (CLIP) service,more particularly to a system and method for implementing the CLIPservice in an Internet Protocol Multimedia Subsystem (IMS).

BACKGROUND OF THE INVENTION

At present, with the continuous development of telecommunicationtechnology, users have increasing demands for the telecommunicationservice, and a number of personalized telecommunication services havecome forth thereby. However, there is no such service that allows acalling terminal to subscribe to multimedia resources used as a ringingprompt for a called terminal. For the convenience of description, suchservice is called a CLIP service for short hereinafter, and themultimedia resources that are subscribed by the calling terminal andused as a ringing prompt to play for the called terminal may include atleast one of image, text, audio and video.

SUMMARY OF THE INVENTION

Embodiments of the present invention provide a system and a method forimplementing a Multimedia Calling Line Identification Presentation(CLIP) service, which enables a calling terminal to subscribe tomultimedia resources for a called terminal.

Embodiments of the present invention also provide an Application Server(AS) for implementing management for the CLIP service; a user terminalas a called terminal of the CLIP service so as to play the multimediaresources subscribed by the calling terminal for the called terminal;and a Multimedia Resource Function (MRF) for playing, for the calledterminal, the multimedia resources subscribed by the calling terminal inthe CLIP service.

A system for implementing a CLIP service includes:

-   -   a resource storage entity, for storing multimedia resources        subscribed by a calling terminal;    -   a resource playing entity, for downloading the multimedia        resources from the resource storage entity and playing the        multimedia resources;    -   a CLIP service management entity, for obtaining a storage        address of the multimedia resources and sending the storage        address of the multimedia resources to the resource playing        entity.

A method for implementing a CLIP service includes:

-   -   storing multimedia resources subscribed by a calling terminal in        a resource storage entity;    -   obtaining, by a CLIP service management entity, a storage        address of the multimedia resources, and sending the storage        address of the multimedia resources to a resource playing        entity;    -   downloading, by the resource playing entity, the multimedia        resources from the resource storage entity according to the        storage address of the multimedia resources, and playing the        multimedia resources.

An AS, as an AS registered by a third party standing for a callingterminal in a CLIP service, includes:

-   -   a multimedia resource notification module, for obtaining a        storage address of multimedia resources subscribed by the        calling terminal and sending the storage address of the        multimedia resources to a resource playing entity after        receiving formal session information sent by the calling        terminal.

A user terminal, as a called terminal in a CLIP service, includes:

-   -   a multimedia resource downloading module, for downloading        multimedia resources from a resource storage entity after        receiving a storage address of the multimedia resources        subscribed by a calling terminal, wherein the storage address of        the multimedia resources is sent by a CLIP service management        entity;    -   a multimedia resource playing module, for playing the multimedia        resources before a called user is off-hook, and stopping playing        the multimedia resources after detecting that the called user is        off-hook.

An MRF includes:

-   -   a multimedia resource downloading module, for downloading        multimedia resources subscribed by a calling terminal from a        resource storage entity after receiving a storage address of the        multimedia resources, wherein the storage address of the        multimedia resources is sent by a CLIP service management        entity;    -   a multimedia resource playing module, for exchanging multimedia        session information with a called terminal, establishing a media        channel for playing the multimedia resources between the        multimedia resource playing module and the called terminal,        playing the multimedia resources for the called terminal through        the media channel, and stopping playing the multimedia resources        after receiving an off-hook event of the called user sent by the        CLIP service management entity.

As can be seen from the above mentioned technical scheme, the multimediaresources subscribed by the calling terminal is stored in the resourcestorage entity accessed by the resource playing entity with thecapability of downloading and playing the multimedia resources. When thecalling terminal calls the called terminal, the CLIP service managemententity sends the storage address of the multimedia resources to theresource playing entity, the resource playing entity then downloads themultimedia resources from the resource storage entity, and plays themultimedia resources for the called terminal when it is needed to play aringing prompt for the called terminal according to the callingprocedure. Therefore, the embodiments of the present invention enablethe calling terminal to subscribe to the multimedia resources for thecalled terminal.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a schematic diagram illustrating a networking structure of anexemplary system for implementing a CLIP service according to anembodiment of the present invention.

FIG. 2 is a schematic diagram illustrating a networking structure ofanother exemplary system for implementing a CLIP service according to anembodiment of the present invention.

FIG. 3 a is a schematic diagram illustrating a structure of the ASaccording to an embodiment of the present invention.

FIG. 3 b is a schematic diagram illustrating a structure of the calledterminal according to an embodiment of the present invention.

FIG. 3 c is a flowchart illustrating an implementation of the CLIPservice in an IMS according to an embodiment of the present invention.

FIG. 4 a is a schematic diagram illustrating a structure of the ASaccording to an embodiment of the present invention.

FIG. 4 b is a schematic diagram illustrating a structure of the MRF inan embodiment of the present invention.

FIG. 4 c is a flowchart illustrating an implementation of the CLIPservice in an IMS according to an embodiment of the present invention.

FIG. 5 is a flowchart illustrating an implementation of the CLIP servicein an IMS according to an embodiment of the present invention.

DETAILED DESCRIPTION OF THE INVENTION

The present invention will be hereinafter described in detail withreference to the accompanying drawings and embodiments. It should beunderstood that the described specific embodiments are only used forillustrating the present invention and not for limiting the presentinvention.

Embodiments of the present invention include: storing multimediaresources subscribed by a calling terminal in a resource storage entitythat may be accessed by a resource playing entity with the capability ofdownloading and playing the multimedia resources; when the callingterminal calls a called terminal, a CLIP service management entitysending a storage address of the multimedia resources to the resourceplaying entity, the resource playing entity then downloading themultimedia resources from the resource storage entity and playing themultimedia resources for the called terminal.

FIG. 1 is a schematic diagram illustrating a networking structure of anexemplary system for implementing a CLIP service according to anembodiment of the present invention. In the exemplary system of FIG. 1,the called terminal is taken as the resource playing entity. In thisembodiment, the called terminal is required to be capable of downloadingand playing multimedia resources.

After the calling terminal subscribes to a CLIP service, multimediaresources subscribed by the calling terminal are stored in a resourcestorage entity that may be accessed by the called terminal, and a CLIPservice management entity may obtain, in real time, the storage addressof the multimedia resources.

The CLIP service management entity is used for, when the callingterminal calls the called terminal, sending the storage address of themultimedia resources to the called terminal.

The called terminal is used for downloading the multimedia resourcesfrom the resource storage entity and, when it is needed to play aringing prompt for the called terminal according to the callingprocedure, playing the multimedia resources.

FIG. 2 is a schematic diagram illustrating a networking structure ofanother exemplary system for implementing a CLIP service according to anembodiment of the present invention. In the exemplary system of FIG. 2,an entity except the called terminal is taken as the resource playingentity with the capability of downloading and playing multimediaresources. In this embodiment, the called terminal is not required to becapable of downloading and playing the multimedia resources.

After the calling terminal subscribes to a CLIP service, multimediaresources subscribed by the calling terminal is stored in a resourcestorage entity that may be accessed by the resource playing entity, anda CLIP service management entity may obtain, in real time, the storageaddress of the multimedia resources.

The CLIP service management entity is used for, when the callingterminal calls the called terminal, sending the storage address of themultimedia resources to the resource playing entity, establishing amedia channel for playing the multimedia resources between the resourceplaying entity and the called terminal by forwarding multimedia sessioninformation exchanged between the resource playing entity and the calledterminal, and instructing the resource playing entity to stop playingthe multimedia resources for the called terminal after receiving anoff-hook event of the called user.

The resource playing entity is used for downloading the multimediaresources from the resource storage entity and, when it is needed toplay a ringing prompt for the called terminal according to the callingprocedure, playing the multimedia resources for the called terminal. Indifferent networks, different network entities may be taken as theresource playing entity, for example in an IMS framework, a MultimediaResource Function (MRF) may be taken as the resource playing entity.

In the following embodiments, an example of implementing a CLIP servicein an IMS framework is taken so as to describe the implementation of theCLIP service.

In the IMS network, services are usually provided by an ApplicationServer (AS), so the AS is taken as a CLIP service management entity inthe following embodiments. Preferably, the AS registered by a thirdparty standing for the calling terminal is taken as the CLIP servicemanagement entity. The AS registered by the third party standing for thecalling terminal means such AS that is registered by the third party,generally a Serving Call Server Management Function (S-CSCF) standingfor the calling terminal.

The First Embodiment

This embodiment adopts the principle of the first exemplary system forimplementing a CLIP service, in other words, the called terminal in thisembodiment is capable of downloading and playing multimedia resources.

In this embodiment, the multimedia resources subscribed by the callingterminal is stored in a resource storage entity that may be addressedthrough a Uniform Resource Locator (URL) address in the IMS network, andan AS that may obtain, in real time, the URL address of the multimediaresources is taken as the CLIP service management entity. Specifically,the URL address of the multimedia resources may be stored in the AS orin such data center as a Home Subscriber Server (HSS) that the AS mayaccess and obtain data from.

FIG. 3 a is a schematic diagram illustrating a structure of the AS inthis embodiment. As shown in FIG. 3 a, the AS in this embodimentincludes:

a multimedia resource notification module, for obtaining a storageaddress of the multimedia resources and sending the storage address ofthe multimedia resources to the called terminal after receiving formalsession information sent by the calling terminal.

Optionally, the AS further includes: a multimedia resource addressstorage module, for storing the storage address of the multimediaresources.

FIG. 3 b is a schematic diagram illustrating a structure of the calledterminal taken as the resource playing entity. As shown in FIG. 3 b, inthis embodiment, the called terminal includes:

a multimedia resource downloading module, used for downloading themultimedia resources from a resource storage entity after receiving thestorage address of the multimedia resources that is sent by the AS;

a multimedia resource playing module, used for playing the multimediaresources before the called user is off-hook, and stopping playing themultimedia resources after detecting that the user is off-hook.

FIG. 3 c is a flowchart illustrating an implementation of the CLIPservice in an IMS in this embodiment. The method for implementing a CLIPservice in the IMS in this embodiment includes the following steps.

Step 301: the calling terminal that has subscribed to multimediaresources sends to the AS an INVITE message containing a SessionDescription Protocol (SDP) message body describing formal sessioninformation. Hereinafter, the SDP message body describing the formalsession information is identified as SDP-1.

Step 302: the AS obtains a URL address of the multimedia resources, addsthe URL address to the INVITE message, and sends the INVITE message tothe called terminal. Specifically, the URL address may be added to aCall-Info header or other optional fields like Alert-Info of the INVITEmessage, or to an extensible Mark Language (XML) script.

The AS may obtain the URL address of the multimedia resources from URLaddress records of multimedia resources stored locally or from a datacenter for storing the URL addresses of multimedia resources, e.g., anHSS.

Step 303: the called terminal downloads the multimedia resources fromthe resource storage entity according to the URL address in the INVITEmessage. Therein, corresponding downloading modes may be adoptedrespectively according to different URL address formats, for exampleHypertext Transfer Protocol (HTTP) or File Transfer Protocol (FTP).

Steps 304 to 307: the called terminal returns a 183 message indicatingthe session progress to the calling terminal through the AS, and the 183message contains an SDP message body SDP-1′ that is used for respondingto the SDP-1 by the called terminal and used for describing negotiatedformal session information. The calling terminal sends a ProvisionalAcknowledgement (PRACK) message in response to the 183 message to thecalled terminal through the AS, and then the called terminal returns a200 OK message in response to the PRACK message to the calling terminalthrough the AS.

Step 308: the called terminal starts playing the multimedia resourcesand sends a 180 message indicating the ringing of the called terminal tothe calling terminal through the AS. The called terminal may startplaying the multimedia resources before sending the 180 message or sendthe 180 message before starting playing the multimedia resources, andthere is no strict execution order.

Steps 309 to 310: when the called user is off-hook, the called terminalsends a 200 OK message indicating the off-hook of the called user to thecalling terminal through the AS. The calling terminal, through the AS,returns an Acknowledgement (ACK) message in response to the 200 OKmessage sent by the called terminal to the called terminal, and then thecalled terminal stops playing the multimedia resources.

Thus far, the CLIP service terminates and a media channel for the formalsession between the calling terminal and the called terminal has beenestablished completely.

The Second Embodiment

This embodiment adopts the principle of the second exemplary system forimplementing a CLIP service, that is, except the called terminal, anentity with the capability of downloading and playing the multimediaresources in the IMS network is taken as the resource playing entity.Generally, an MRF is taken as the resource playing entity in the IMS.The MRF may play the multimedia resources for the called terminal by aReal-time Transfer Protocol (RTP) media stream mode. Accordingly, themultimedia resources in this embodiment may be played by the RTP mediastream mode.

In this embodiment, the multimedia resources subscribed by the callingterminal is stored in a resource storage entity in the IMS that may beaddressed through a URL address, and the AS which may obtain, inreal-time, the URL address of the multimedia resources is taken as aCLIP service management entity. Specifically, the URL address of themultimedia resources may be stored in the AS or in a data center whichmay be accessed by the AS, such as an HSS.

FIG. 4 a is a schematic diagram illustrating a structure of the AS inthis embodiment. In this embodiment, the AS includes:

a multimedia resource notification module, used for obtaining a storageaddress of the multimedia resources and sending the storage address toan MRF after receiving formal session information sent by the callingterminal;

a CLIP service management module, used for establishing a media channelfor playing the multimedia resources between the MRF and the calledterminal by forwarding multimedia session information exchanged betweenthe MRF and the called terminal, and instructing the MRF to stop playingthe multimedia resources for the called terminal after receiving anoff-hook event of the called user.

Optionally, the AS further includes a multimedia resource addressstorage module, which is used for storing the storage address of themultimedia resources.

FIG. 4 b is a schematic diagram illustrating a structure of the MRF inthis embodiment. As shown in FIG. 4 b, in this embodiment, the MRFincludes:

a multimedia resource downloading module, used for downloading themultimedia resources from a resource storage entity after receiving thestorage address of the multimedia resources that is sent by the AS;

a multimedia resource playing module, used for exchanging the multimediasession information with the called terminal, establishing a mediachannel for playing the multimedia resources between the multimediaresource playing module and the called terminal, playing the multimediaresources for the called terminal through the media channel, andstopping playing the multimedia resources for the called terminal afterreceiving an off-hook event of the called user sent by the AS.

FIG. 4 c is a flowchart illustrating an implementation of the CLIPservice in an IMS in this embodiment. As shown in FIG. 4, theimplementation of a CLIP service in the IMS includes the followingsteps.

Step 401: the calling terminal that has subscribed to multimediaresources sends to the AS an INVITE message containing an SDP messagebody describing formal session information. Hereinafter, the SDP messagebody describing the formal session information is identified as SDP-1.

Step 402: the AS deletes the SDP-1 from the INVITE message, adds a URLaddress of the multimedia resources to the INVITE message and then sendsthe INVITE message to the MRF. Specifically, the URL address may beadded to a Call-Info header or other optional fields like Alert-Info ofthe INVITE message, or to an XML script.

Step 403: the MRF downloads the multimedia resources from the resourcestorage entity according to the URL address in the INVITE message.Corresponding downloading modes may be adopted respectively, such as HTTor FTP, according to different URL address formats.

Step 404: the MRF returns to the AS a 200 OK message containing the SDPmessage body describing session information of the MRF playing themultimedia resources for the called terminal. The session of the MRFplaying the multimedia resources for the called terminal is called amultimedia session for short hereinafter, and the SDP message bodydescribing the session information of the MRF playing the multimediaresources is identified as SDP-2 in this embodiment.

Step 405: the AS adds the SDP-2 to the INVITE message sent by thecalling terminal and sends the INVITE message to the called terminal.The INVITE message sent by the AS to the called terminal contains boththe SDP-1 and the SDP-2.

Step 406: the called terminal returns to the AS a 183 message containingan SDP message body SDP-1′ for responding to the SDP-1 by the calledterminal and an SDP message body SDP-2′ for responding to the SDP-2 bythe called terminal. Specifically, the SDP-1′ is used for describingnegotiated formal session information, while the SDP-2′ is used fordescribing negotiated multimedia session information.

Steps 407 to 409: the AS deletes the SDP-2′ from the 183 message andreturns the 183 message to the calling terminal. The calling terminalsends a PRACK message in response to the 183 message to the calledterminal through the AS, and the called terminal returns a 200 OKmessage in response to the PRACK message to the calling terminal throughthe AS.

Step 410: the AS returns the ACK message containing the SDP-2′ to theMRF.

Thus far, a media channel for the multimedia session between the MRF andthe called terminal has been established completely.

Steps 411 to 414: the called terminal sends a 180 message to the AS, theAS sends to the MRF an INFO message instructing the MRF to start playingthe multimedia resources, the MRF returns a 200 OK message in responseto the INFO message to the AS and starts playing the multimediaresources for the called terminal through the media channel between theMRF and the called terminal, and then the AS forwards the 180 message tothe calling terminal.

Steps 415 to 417: when the called user is off-hook, the called terminalsends to the AS a 200 OK message indicating the off-hook of the calleduser. The AS sends to the MRF a BYE message instructing the MRF to stopplaying the multimedia resources, the MRF stops playing the multimediaresources for the called terminal through the media channel between theMRF and the called terminal, and then returns a 200 OK message inresponse to the BYE message to the AS.

Thus far, the CLIP service terminates.

Steps 418 to 419: the AS forwards to the calling terminal the 200 OKmessage indicating the off-hook of the called user. The calling terminalreturns to the called terminal an ACK message for responding the 200 OKmessage sent by the calling terminal through the AS.

Hereby, a media channel for the formal session between the callingterminal and the called terminal has been established completely.

It should be noted that, the CLIP service is a kind of callingsubscription service, and the calling user may either subscribe to orcancel the CLIP service. If the calling user has subscribed to the CLIPservice, the multimedia resources may be used during the callingprocedure; otherwise, such CLIP service may not be used. The calledterminal may determine whether to accept the multimedia resourcessubscribed by the calling terminal as required. For example, the calleduser may determine to display the multimedia resources by subscribing toa multimedia resource display service. If the called user has subscribedto the multimedia resource display service, the multimedia resourceswill be displayed; otherwise, the multimedia resources will not bedisplayed. The called user may determine not to display the multimediaresources by subscribing to a multimedia resource display restrictionservice. If the called user has subscribed to the multimedia resourcedisplay restriction service, the multimedia resources will not bedisplayed; otherwise, the multimedia resources will be displayed.

The Third Embodiment

The present embodiment also adopts the principle of the second exemplarysystem for implementing a CLIP service. The main difference from thesecond embodiment lies in: the second embodiment adopts an earlier mediascheme of an application server model, namely using two SDP messagebodies, one SDP message body is used for describing the formal sessioninformation, while the other SDP message body is used for describing themultimedia session information. Embodiments of the present inventionadopt an earlier media scheme of a gateway model, namely that one SDPmessage body is used for describing both the formal session informationand the multimedia session information, that is, one part of the SDPmessage body is used for describing the formal session information andthe other part is used for describing the multimedia sessioninformation.

The AS and the MRF in this embodiment have the same structures as the ASin FIG. 4 a and the MRF in FIG. 4 b respectively, so no more descriptionis made in detail.

FIG. 5 is a flowchart illustrating an implementation of the CLIP servicein an IMS in this embodiment. As shown in FIG. 5, the implementation ofa CLIP service in the IMS includes the following steps.

Step 501: the calling terminal that has subscribed to multimediaresources sends to the AS an INVITE message containing an SDP messagebody describing formal session information. Hereinafter, the SDP messagebody describing the formal session information is identified as SDP-1.

Step 502: the AS deletes the SDP-1 from the INVITE message, adds a URLaddress of the multimedia resources to the INVITE message and then sendsthe INVITE message to the MRF. Specifically, the URL address may beadded to a Call-Info header or other optional fields like Alert-Info ofthe INVITE message, or to an XML script.

Step 503: the called terminal downloads the multimedia resources from aresource storage entity according to the URL address in the INVITEmessage. Corresponding downloading modes may be adopted respectively,such as HTTP or FTP, according to different URL address formats.

Step 504: the MRF returns to the AS a 200 OK message containing an SDPmessage body describing the multimedia session information. The SDPmessage body describing the multimedia session information is identifiedas SDP-2.

Step 505: the AS constructs an SDP message body describing both theformal session information and the multimedia session information, andthe SDP message body newly constructed is called SDP-3 for shorthereinafter. The AS deletes the SDP-1 from the INVITE message sent bythe calling terminal, adds the SDP-3 to the INVITE message and thensends the INVITE message to the called terminal.

Step 506: the called terminal returns to the AS a 183 message containingan SDP message body SDP-3′ for responding to the SDP-3 by the calledterminal, in other words, the SDP-3′ is used for describing bothnegotiated formal session information and negotiated multimedia sessioninformation simultaneously.

Step 507: the AS deletes the part describing the negotiated multimediasession information from the SDP-3′, hereinafter, the SDP-3′ that hasgone through the deleting process is identified as SDP-4′. The AS sendsa 183 message containing the SDP-4′ to the calling terminal. The SDP-4′only describes the negotiated formal session information.

Steps 508 to 509: the calling terminal sends to the called terminal aPRACK message in response to the 183 message sent by the AS through theAS, and then the called terminal returns to the calling terminal a 200OK message in response to the PRACK message through the AS.

Step 510: the AS deletes the part describing the negotiated formalsession information from the SDP-3′. Hereinafter, the SDP-3′ that hasgone through the deleting process is identified as SDP-5′. The AS sendsto the MRF an ACK message containing the SDP-5′. The SDP-5′ onlydescribes the negotiated multimedia session information.

Thus far, the media channel for the multimedia session between the MRFand the called terminal has been established completely.

Steps 511 to 514: the called terminal sends a 180 message to the AS, theAS sends to the MRF an INFO message instructing the MRF to start playingthe multimedia resources, the MRF returns a 200 OK message in responseto the INFO message to the AS and starts playing the multimediaresources for the called terminal through the media channel between theMRF and the called terminal, and then the AS forwards the 180 message tothe calling terminal.

Steps 515 to 517: when the called user is off-hook, the called terminalsends to the AS a 200 OK message indicting the off-hook of the calleduser. The AS sends to the MRF a BYE message instructing the MRF to stopplaying the multimedia resources. The MRF stops playing multimediaresources for the called terminal through the media channel between theMRF and the called terminal, and then returns a 200 OK message inresponse to the BYE message to the AS.

Thus far, the CLIP service terminates.

Steps 518 to 521: the AS sends to the called terminal a UPDATE messagefor notifying the called terminal to modify the attribute of themultimedia session information part in the SDP-3′ into deactivation, bywhich the called terminal may stop receiving the multimedia resources.The called terminal modifies the attribute of the multimedia sessioninformation part in the SDP-3′ into the deactivation, stops receivingthe multimedia resources and returns a 200 OK message in response to theUPDATE message to the AS. The AS forwards the 200 OK message indicatingthe off-hook of the called user to the calling terminal, and then thecalling terminal returns an ACK message in response to the 200 OKmessage to the called terminal through the AS.

Hereby, the media channel for the formal session between the callingterminal and called terminal has been established completely.

The foregoing description is only a preferred embodiment of thisinvention and is not for use in limiting the protection scope thereof.All the modifications, equivalent replacements or improvements in thescope of the present invention's spirit and principles shall be includedin the protection scope of the present invention.

1. An apparatus, comprising: a multimedia resource notification module,which obtains a storage address of a multimedia resource that is storedby a resource storage entity and that is subscribed to by a callingterminal, and which sends the storage address of the multimedia resourceto a resource playing entity after receiving formal session informationfrom the calling terminal; and a service management module, whichestablishes a media channel between the resource playing entity and thecalled terminal for playing the multimedia resource, by at least:sending multimedia session information to the called terminal, themultimedia session information having been received by the servicemanagement module from the resource playing entity; and sendingnegotiated multimedia session information to the resource playingentity, the negotiated multimedia session information having beenreceived by the service management module from the called terminal. 2.The apparatus of claim 1, wherein, based on establishing the mediachannel, the resource playing entity is enabled to download themultimedia resource from the resource storage entity according to thestorage address of the multimedia resource and to play the multimediaresource for the called terminal through the media channel.
 3. Theapparatus of claim 1, wherein the service management module comprises aCall Line Identification Presentation (CLIP) service management module.4. The apparatus of claim 1, wherein the apparatus comprises anApplication Server (AS).
 5. The apparatus of claim 4, wherein theresource storage entity is accessed by the AS or in the AS.
 6. Theapparatus of claim 1, wherein the resource playing entity comprises aMultimedia Resource Function (MRF).
 7. The apparatus of claim 1, whereinthe apparatus implements a Multimedia Calling Line IdentificationPresentation (CLIP) service.
 8. A computer program product comprisingone or more non-transitory computer-readable media having stored thereoncomputer-executable instructions that, when executed by one or moreprocessors of a computer system, cause the computer system to perform atleast the following: obtaining, by a service management entity, astorage address of a multimedia resource subscribed to by a callingterminal; sending, by the service management entity, the storage addressof the multimedia resource to a resource playing entity after thecalling terminal initiates a session, wherein the multimedia resourcesubscribed to by the calling terminal is stored in a resource storageentity; and establishing, by the service management entity, a mediachannel between the resource playing entity and a called terminal,including: sending multimedia session information to the calledterminal, the multimedia session information having been received by theservice management entity from the resource playing entity; and sendingnegotiated multimedia session information to the resource playingentity, the negotiated multimedia session information having beenreceived by the service management entity from the called terminal. 9.The computer program product of claim 8, wherein, based on the servicemanagement entity establishing the media channel between the resourceplaying entity and the called terminal, the resource playing entitydownloads the multimedia resource from the resource storage entityaccording to the storage address of the multimedia resource and playsthe multimedia resource for the called terminal through the mediachannel.
 10. The computer program product of claim 8, wherein theservice management entity comprises a Calling Line IdentificationPresentation (CLIP) service management entity, and the resource playingentity comprises a Multimedia Resource Function (MRF).
 11. The computerprogram product of claim 8, wherein obtaining the storage address of themultimedia resource comprises one of: obtaining, by the servicemanagement entity, a URL address of the multimedia resource that hasbeen stored by the service management entity; or downloading, by theservice management entity, a URL address of the multimedia resource of aHome Subscriber Server (HSS) accessed by the service management entity.12. The computer program product of claim 8, wherein sending the storageaddress of the multimedia resource to the resource playing entitycomprises: adding, by the service management entity, a URL address ofthe multimedia resource to an INVITE message; and sending, by theservice management entity, the INVITE message to the resource playingentity.
 13. The computer program product of claim 12, wherein the URLaddress of the multimedia resource is added to a Call-Info header or anAlert-Info field of the INVITE message, or to an extensible MarkLanguage (XML) script.
 14. The computer program product of claim 8,wherein the resource playing entity plays the multimedia resource forthe called terminal when the called terminal rings, and furthercomprising: instructing, by the service management entity, the resourceplaying entity to stop playing the multimedia resource for the calledterminal after receiving an off-hook event of a called user.
 15. Thecomputer program product of claim 14, further comprising: notifying, bythe service management entity, the called terminal to stop receiving themultimedia resource; and notifying, by the service management entity,the calling terminal of the off-hook event of the called user, so as tostart a session between the calling terminal and the called terminal.16. An application server, comprising: one or more hardware processors;and one or more non-transitory computer-readable storage devices havingstored thereon computer-executable instruction that, when executed bythe one or more hardware processors, cause a service management entityof the application server to perform at least the following: obtain astorage address of a multimedia resource subscribed to by a callingterminal; send the storage address of the multimedia resource to aresource playing entity after the calling terminal initiates a session,wherein the multimedia resource subscribed to by the calling terminal isstored in a resource storage entity; and establish a media channelbetween the resource playing entity and a called terminal, including:sending multimedia session information to the called terminal, themultimedia session information having been received by the servicemanagement entity from the resource playing entity; and sendingnegotiated multimedia session information to the resource playingentity, the negotiated multimedia session information having beenreceived by the service management entity from the called terminal. 17.The application server of claim 16, wherein, based on the servicemanagement entity establishing the media channel between the resourceplaying entity and the called terminal, the resource playing entitydownloads the multimedia resource from the resource storage entityaccording to the storage address of the multimedia resource and playsthe multimedia resource for the called terminal through the mediachannel.
 18. The application server of claim 16, wherein sending thestorage address of the multimedia resource to the resource playingentity after the calling terminal initiates the session occurs beforethe session is established.
 19. The application server of claim 16,wherein a mode of sending the multimedia resource is a HypertextTransfer Protocol (HTTP) mode or a File Transfer Protocol (FTP) mode,and wherein the storage address of the multimedia resource is a UniformResource Locator (URL) address.
 20. The application server of claim 16,wherein the service management entity comprises a Calling LineIdentification Presentation (CLIP) service management entity, and theresource playing entity comprises a Multimedia Resource Function (MRF).